<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en" xml:lang="en" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Glossary - OpenUP</title>
</head>
<body text="#000000" bgcolor="#ffffff">
<font face="Arial, Helvetica, sans-serif">
<dl>
<dt>
<b><a id="_GLOSSARY_ITEM_A" name="A">A</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_activity" name="activity">activity</a></b>
</dt>
<dd><p>     In the <a  class="elementLink" href="#uma" guid="_cj6jkB_PEdq6CKKKq4D7YA" >UMA</a>&nbsp;, an activity is a <a  class="elementLink" href="#breakdown_element" guid="_cvdpEB_LEdq6CKKKq4D7YA" >breakdown element</a>&nbsp;which supports the nesting and logical grouping of related     process elements such as <a  class="elementLink" href="#descriptor" guid="_7rS6AB_JEdq6CKKKq4D7YA" >descriptor</a>&nbsp;and sub-activities, thus forming <a  class="elementLink" href="#breakdown_structure" guid="_95LCoB_QEdq6CKKKq4D7YA" >breakdown structure</a>s. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_activity_detail_diagram" name="activity_detail_diagram">activity detail diagram</a></b>
</dt>
<dd>Diagram depicting all the <a  class="elementLink" href="#breakdown_element" guid="_cvdpEB_LEdq6CKKKq4D7YA" >breakdown element</a>s within the scope of the selected process element. This diagram also depicts input/output relationships between <a  class="elementLink" href="#task" guid="_x459ktnmEdmO6L4XMImrsA" >task</a>s,&nbsp;activities, and <a  class="elementLink" href="#work_product" guid="_H4JXwB_SEdq6CKKKq4D7YA" >work product</a>s;&nbsp;as well as responsibility relationships between <a  class="elementLink" href="#role" guid="_yUefQNnmEdmO6L4XMImrsA" >role</a>s and tasks. Activity detail diagrams are used to provide a complete summary of an activity&nbsp;and thus&nbsp;improve their comprehensibility.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_agile" name="agile">agile</a></b>
</dt>
<dd>A set of values and principles for software development that use lean production techniques to deliver value to stakeholders quickly and frequently. See the agile manifesto at: <a  href="http://agilemanifesto.org/" >http://agilemanifesto.org/</a></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_architectural_mechanism" name="architectural_mechanism">architectural mechanism</a></b>
</dt>
<dd>Architectural mechanisms represent common concrete solutions to frequently encountered problems. They may be patterns of structure, patterns of behavior, or both.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_architectural_view" name="architectural_view">architectural view</a></b>
</dt>
<dd>A view of the&nbsp;architecture from a given perspective.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_architecture" name="architecture">architecture</a></b>
</dt>
<dd><p>     Describes the blueprint for software development, frequently represented using a number of architectural views. It also     contains the rationale, assumptions, explanations and implications of the decisions that were made in forming the     architecture as well as the global mapping between views. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_artifact" name="artifact">artifact</a></b>
</dt>
<dd>Artifacts are a specialized type of <a  class="elementLink" href="#work_product" guid="_H4JXwB_SEdq6CKKKq4D7YA" >work product</a> that represents tangible, non-trivial items that are consumed, produced, or modified by tasks. Artifacts may be composed of other artifacts and often serve as a basis for defining reusable assets.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_assists" name="assists">assists</a></b>
</dt>
<dd>Describes roles that may be consulted on task but are not actually assigned to perform the work.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_B" name="B">B</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_breakdown_element" name="breakdown_element">breakdown element</a></b>
</dt>
<dd>Any element modeled in <a  class="elementLink" href="#uma" guid="_cj6jkB_PEdq6CKKKq4D7YA" >UMA</a>&nbsp;that is part of <a  class="elementLink" href="#process" guid="_yQ5m2NnmEdmO6L4XMImrsA" >process</a>&nbsp;structure.<!--EndFragment--></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_breakdown_structure" name="breakdown_structure">breakdown structure</a></b>
</dt>
<dd><p>     A <a  class="elementLink" href="#uma" guid="_cj6jkB_PEdq6CKKKq4D7YA" >UMA</a>&nbsp;construct that specifies a <a  class="elementLink" href="#process" guid="_yQ5m2NnmEdmO6L4XMImrsA" >process</a>&nbsp;as the hierarchical composition of <a  class="elementLink" href="#breakdown_element" guid="_cvdpEB_LEdq6CKKKq4D7YA" >breakdown element</a>s. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_build" name="build">build</a></b>
</dt>
<dd>An operational version of a system or part of a system that demonstrates a subset of the capabilities to be provided in the final product</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_C" name="C">C</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_capability_pattern" name="capability_pattern">capability pattern</a></b>
</dt>
<dd><p>     <!--StartFragment-->A&nbsp;special type of&nbsp;<a  class="elementLink" href="#process" guid="_yQ5m2NnmEdmO6L4XMImrsA" >process</a>&nbsp;used to define a stereotypical way of performing work related to a     particular subject.&nbsp; Capability Patterns are often used as course grained building blocks to assemble delivery     processes.<!--EndFragment--> </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_checklist" name="checklist">checklist</a></b>
</dt>
<dd>A specialized type of guidance that identifies a series of items that need to be completed or verified. Checklists are often used in reviews such as walkthroughs or inspections.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_code_instrumentation" name="code_instrumentation">code instrumentation</a></b>
</dt>
<dd>&nbsp;"Extra" statements added to source code for the purposes of testing, debugging, tuning,&nbsp;or tracing.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_component" name="component">component</a></b>
</dt>
<dd><p>     An encapsulated part of the system that is nontrivial, nearly independent, and replaceable and that fulfils a clear     function in the context of well-defined architecture. A component conforms to and provides the realization of a set of     interfaces. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_composite_role" name="composite_role">composite role</a></b>
</dt>
<dd>A special role descriptor that relates to more than one <a  class="elementLinkWithUserText" href="#role" guid="_yUefQNnmEdmO6L4XMImrsA" >role</a>. It represents a grouping of roles with the main purpose of reducing the number of roles defined in method content for a process.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_concept" name="concept">concept</a></b>
</dt>
<dd>A specialized type of guidance that outlines key ideas or basic principles that serve as foundation for additional information.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_configuration" name="configuration">configuration</a></b>
</dt>
<dd>The performance, functional, and physical attributes of an existing or planned product, or a combination of products.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_construction" name="construction">Construction</a></b>
</dt>
<dd>The third phase of the project lifecycle in which the software is brought from  an executable architectural baseline to the point at which it is ready to be transitioned  to the user community.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_custom_category" name="custom_category">custom category</a></b>
</dt>
<dd>Used to categorize content based on the user's criteria. One important use is for constructing <a  class="elementLinkWithUserText" href="#view" guid="_GH6WUMaJEduMlb2cQZNTYw" >views</a>&nbsp;for publishing.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_D" name="D">D</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_deliverable" name="deliverable">deliverable</a></b>
</dt>
<dd><p>     A&nbsp;specialized type of work prodcut&nbsp;used to define the primary outputs that represent value, material or     otherwise,&nbsp;to the client, customer or other stakeholders.&nbsp; These are typically the result of packaging     other&nbsp;work products for sign-off and delivery. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_delivery_process" name="delivery_process">delivery process</a></b>
</dt>
<dd>A delivery process is a special <a  class="elementLink" href="#process" guid="_yQ5m2NnmEdmO6L4XMImrsA" >process</a> describing a complete and integrated approach for performing a specific project type. <!--StartFragment-->It provides a complete end-to-end lifecycle (for it's scope) and can be used as a reference for running projects with similar characteristics.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_descriptor" name="descriptor">descriptor</a></b>
</dt>
<dd>Defines how method content is represented in a process.&nbsp;&nbsp;Descriptors are the key concept for realizing the separation of proces&nbsp;from metho content.&nbsp;A&nbsp;descriptor&nbsp;has its own relationships and properties which can be modified independent of the default relationships&nbsp;defined in the method content.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_discipline" name="discipline">discipline</a></b>
</dt>
<dd><p>     Primary categorization mechanism for organizing&nbsp;tasks that&nbsp;define&nbsp;a major 'area of concern' and/or     cooperation of work effort. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_discipline_grouping" name="discipline_grouping">discipline grouping</a></b>
</dt>
<dd>A collection of related disciplines defined for a specific usage or context.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_domain" name="domain">domain</a></b>
</dt>
<dd><p>     Primary catgorization mechanism for organizing work products that have an affinity to each other based on resources,     timing, relationships or general subject area. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_E" name="E">E</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_effort" name="effort">effort</a></b>
</dt>
<dd><p>     The number of labor units required to complete an activity or other project element. Usually expressed as staff hours,     staff days, or staff weeks. Should not be confused with duration. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_elaboration" name="elaboration">Elaboration</a></b>
</dt>
<dd>Second of four phases in the project lifecycle, when architecturally significant  risks are addressed.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_estimation_considerations" name="estimation_considerations">estimation considerations</a></b>
</dt>
<dd>A specialized type&nbsp;of guidance&nbsp;that describes&nbsp;the amount of effort to produce a work product&nbsp;or perform a task&nbsp;including any influencing factors.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_example" name="example">example</a></b>
</dt>
<dd><p>     A specialized type&nbsp;of&nbsp; guidance&nbsp;used to include typical samples of the items to be produced, may often     only be a partial sample that is intended as further guidance rather than something to be reused. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_F" name="F">F</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_feature" name="feature">feature</a></b>
</dt>
<dd>An externally observable service provided by the system that directly fulfills a <a  class="elementLink" href="#stakeholder_need" guid="_WUiFcAeYEduWycDgioo5rg" >stakeholder need</a>.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_furps" name="furps">FURPS+</a></b>
</dt>
<dd>Functional, usability, reliability, performance, supportability&nbsp;and others. This acronym represents categories that can be used in the definition of product requirements.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_G" name="G">G</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_guidance" name="guidance">guidance</a></b>
</dt>
<dd><p>     General term referring to all types of material that provide additional detail on other types of elements. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_guideline" name="guideline">guideline</a></b>
</dt>
<dd>A specialized type of&nbsp;<a  class="elementLinkWithUserText" href="#guidance" guid="_83ttAB_NEdq6CKKKq4D7YA" >guidance</a>&nbsp;that provides additional detail on how to handle a particular <a  class="elementLink" href="#method_element" guid="_4svVUO7bEdyYoPJ0YfnNbQ" >method element</a>. Guidelines most commonly describe how to perform some set of actions related to&nbsp;<a  class="elementLinkWithUserText" href="#task" guid="_x459ktnmEdmO6L4XMImrsA" >tasks</a> or provide additional rules or recommendations related to the representation of <a  class="elementLinkWithUserText" href="#work_product" guid="_H4JXwB_SEdq6CKKKq4D7YA" >work products</a>.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_I" name="I">I</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_inception" name="inception">Inception</a></b>
</dt>
<dd>First of the four phases in the project lifecycle.&nbsp;It is about understanding  the project scope and objectives and getting enough information to confirm whether  the project should proceed&nbsp;or not.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_ioc_milestone" name="ioc_milestone">Initial Operational Capability Milestone</a></b>
</dt>
<dd><p> Third major project milestone that occurs at the end of the <a  class="elementLink" href="#construction" guid="_0sD60EvDEdunZcj9T5hrMQ" >Construction</a>    phase. At this point, the product is ready to be handed over to the Transition    team. All functionality has been developed and all alpha testing (if any) has    been completed. In addition to the software, a user manual has been developed,    and there is a description of the current release. The product is ready for    beta testing. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_input" name="input">input</a></b>
</dt>
<dd>In the <a  class="elementLink" href="#uma" guid="_cj6jkB_PEdq6CKKKq4D7YA" >UMA</a>, input defines the&nbsp;<a  class="elementLink" href="#work_product" guid="_H4JXwB_SEdq6CKKKq4D7YA" >work product</a>s needed to perform a <a  class="elementLink" href="#task" guid="_x459ktnmEdmO6L4XMImrsA" >task</a>.&nbsp; These inputs are further categorized as being optional, mandatory or external.&nbsp; Optional inputs may be excluded from the task in some cases without consequences, while without mandatory inputs it is typically not possible to complete the task.&nbsp; External inputs are used to defined mandatory inputs that are the result of work outside the scope of the defined process.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_iteration" name="iteration">iteration</a></b>
</dt>
<dd><p>     A grouping of repeatable activities based on a set period of time&nbsp;that produces an expected set of results that     has value.&nbsp; These results may be further refined in successive iterations. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_iteration" name="iteration">Iteration</a></b>
</dt>
<dd>Short and set duration division of a project. Iterations allow you to demonstrate incremental value and obtain early and continuous feedback.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_iteration_burndown" name="iteration_burndown">Iteration Burndown</a></b>
</dt>
<dd>A primary report for understanding the status of an iteration. It shows the trend for how much work is left to do within that iteration.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_L" name="L">L</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_lca_milestone" name="lca_milestone">Lifecycle Architecture Milestone</a></b>
</dt>
<dd><p>     Second major project milestone that occurs at the end of <a  class="elementLink" href="#elaboration" guid="_8DkT4EvDEdunZcj9T5hrMQ" >Elaboration</a> phase. At this point, a baseline of requirements is agreed     to.&nbsp;Examine the detailed system objectives and scope, the choice of architecture, and the resolution of the major     risks. The milestone is achieved when the architecture has been validated. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_lco_milestone" name="lco_milestone">Lifecycle Objectives Milestone</a></b>
</dt>
<dd><p> First major project milestone, which occurs at the end of the <a  class="elementLink" href="#inception" guid="_525A8EvDEdunZcj9T5hrMQ" >Inception</a>&nbsp;phase.&nbsp;At    this point, compare the cost to the benefits of the project, and decide whether    to proceed with the project or to cancel it. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_M" name="M">M</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_method_architecture" name="method_architecture">method architecture</a></b>
</dt>
<dd>A method architecture defines the concepts, their properties, and relationships for defining methods and processes. It is typically compromised of a meta-model, modeling language, or schema (synonyms) that is used for organizing large amounts of descriptions for management development methods and processes, such as software engineering, mechanical engineering, business transformation, sales cycles etc.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_method_configuration" name="method_configuration">method configuration</a></b>
</dt>
<dd>A method configuration specifies the selection of a logical subset of a <a  class="elementLinkWithUserText" href="#method_library" guid="_1xELEMaFEduMlb2cQZNTYw" >method library</a>, defined in terms of selected packages within plug-ins and any necessary views.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_method_content" name="method_content">method content</a></b>
</dt>
<dd><p>     Defines the primary reusable building blocks or reference materials of the method framework that exist outside of any     predefined lifecycle.&nbsp;The basic content elements are: <a  class="elementLink" href="#role" guid="_yUefQNnmEdmO6L4XMImrsA" >role</a>s, <a  class="elementLink" href="#task" guid="_x459ktnmEdmO6L4XMImrsA" >task</a>s, <a  class="elementLink" href="#work_product" guid="_H4JXwB_SEdq6CKKKq4D7YA" >work product</a>s and <a  class="elementLink" href="#guidance" guid="_83ttAB_NEdq6CKKKq4D7YA" >guidance</a>. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_method_element" name="method_element">method element</a></b>
</dt>
<dd>There are two kinds of method element: &nbsp;<a  class="elementLink" href="#method_content" guid="_Ts2joB_MEdq6CKKKq4D7YA" >method content</a>&nbsp;and <a  class="elementLink" href="#process" guid="_yQ5m2NnmEdmO6L4XMImrsA" >process</a>.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_method_library" name="method_library">method library</a></b>
</dt>
<dd>A&nbsp;physical container for <a  class="elementLinkWithUserText" href="#method_plugin" guid="_D4TLgMaGEduMlb2cQZNTYw" >method plug-ins</a> and <a  class="elementLinkWithUserText" href="#method_configuration" guid="__V7pAMaEEduMlb2cQZNTYw" >method configuration</a> definitions. All&nbsp;<a  class="elementLink" href="#method_element" guid="_4svVUO7bEdyYoPJ0YfnNbQ" >method element</a>s are stored in a method library.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_method_plugin" name="method_plugin">method plug-in</a></b>
</dt>
<dd>Represents a physical container for <a  class="elementLink" href="#method_element" guid="_4svVUO7bEdyYoPJ0YfnNbQ" >method element</a>s.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_milestone" name="milestone">milestone</a></b>
</dt>
<dd><p>     A significant event in the project or sub-project, such as a major decision, completion of a deliverable, or meeting of     a major dependency (like completion of a phase). </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_O" name="O">O</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_outcome" name="outcome">outcome</a></b>
</dt>
<dd><p>     <!--StartFragment-->Specialized type of <a  class="elementLink" href="#work_product" guid="_H4JXwB_SEdq6CKKKq4D7YA" >work product</a>s used to descibe intangible items such as the completion of some set of     activities, a result or state. A key differentiator for outcomes against artifacts is that outcomes are not candidates     for harvesting as reusable assets. Outcomes can not have associated templates or examples and are not possible to reuse     as assets on other projects. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_output" name="output">output</a></b>
</dt>
<dd>Defines the results of performing some task in terms of the <a  class="elementLink" href="#work_product" guid="_H4JXwB_SEdq6CKKKq4D7YA" >work product</a>s produced or modifed.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_P" name="P">P</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_pattern" name="pattern">pattern</a></b>
</dt>
<dd>Generalized solution that can be implemented and applied in a problem situation (a context)</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_performer" name="performer">performer</a></b>
</dt>
<dd>Describes the roles that will be executing a task.&nbsp; There are two types of performs roles, a single primary performer responsible for the completion of the tasks and additional performers.&nbsp; There may be any number of additional performers and both are consided as allocated resources for the purposed of project scheduling.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_phase" name="phase">phase</a></b>
</dt>
<dd><p>     A specialized type of activity&nbsp;that represents a significant period in a project normally ending with a decision     checkpoint, major milestones, or a set of deliverables.&nbsp; Phases typically have well defined objectives and provide     the basis for how the project work will be structured. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_point" name="point">Point</a></b>
</dt>
<dd>A relative measure of size that is typically used for Agile estimation.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_practice" name="practice">practice</a></b>
</dt>
<dd>A specialized type&nbsp;of&nbsp;<a  class="elementLinkWithUserText" href="#guidance" guid="_83ttAB_NEdq6CKKKq4D7YA" >guidance</a> that describes&nbsp;a proven way&nbsp;of doing something or common approaches and strategies that represent best practices.&nbsp; This is also used to&nbsp;represent standards and policies related to methods.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_process" name="process">process</a></b>
</dt>
<dd><p>     Describes the assembly of method content&nbsp;in a sequence or workflow that defines how the work will be executed.     There are two types of processes:&nbsp; <a  class="elementLink" href="#capability_pattern" guid="_2RUJACO4EdqaNq6Ptg8uyA" >capability pattern</a>s and <a  class="elementLink" href="#delivery_process" guid="_ZufeMCO3EdqaNq6Ptg8uyA" >delivery process</a>es. </p><!--EndFragment--><!--EndFragment--></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_pr_milestone" name="pr_milestone">Product Release Milestone</a></b>
</dt>
<dd><p> Fourth major project milestone that occurs at the end of the <a  class="elementLink" href="#transition" guid="_-5ms4EvDEdunZcj9T5hrMQ" >Transition</a>&nbsp;phase.    At this point, decide whether the objectives were met and whether you should    start another development cycle. This milestone&nbsp;is the result of the customer    reviewing and accepting the project deliverables. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_project_burndown" name="project_burndown">project burndown</a></b>
</dt>
<dd><p>     A&nbsp;primary report for understanding the status of&nbsp;a project. It typically consists of&nbsp;a     chart&nbsp;showing&nbsp;the iterations in the horizontal axis and the remaining points from the work items list in the     vertical axis. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_R" name="R">R</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_report" name="report">report</a></b>
</dt>
<dd>A&nbsp;specialized type&nbsp;of&nbsp;&nbsp;<a  class="elementLinkWithUserText" href="#guidance" guid="_83ttAB_NEdq6CKKKq4D7YA" >guidance</a> used to provide guidance on representing the output of an automated tool that may be a combination of information from one or more other work products. .</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_requirement" name="requirement">Requirements</a></b>
</dt>
<dd><ol>     <li>         A capability needed by the user to solve a problem [in order to] to achieve an objective     </li>     <li>         A capability that must be met or possessed by a system or system component to satisfy a contract, standard,         specification, or other formally imposed documentation <a  class="elementLinkWithUserText" href="../core.tech.common.base/guidances/supportingmaterials/references.tech_6CCF393.html" guid="_9ToeIB83Edqsvps02rpOOg" >[THA00]</a><br />     </li> </ol></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_reusable_asset" name="reusable_asset">reusable asset</a></b>
</dt>
<dd>A specialized type&nbsp;of <a  class="elementLinkWithUserText" href="#guidance" guid="_83ttAB_NEdq6CKKKq4D7YA" >guidance</a> linking to intellectual capital that can be utilized to perform some task or leveraged as a starting point for the creation of a solution.&nbsp; This type of guidance&nbsp;is usually represented a link to some external source.&nbsp; This may include assets such as source code, templates, patterns, architectural frameworks, domain models, and so on - that can be reused in a different contexts.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_risk" name="risk">risk</a></b>
</dt>
<dd><p>     A potential event or future situation that can potentially affect, prevent, or limit a project's success. Project risks     may be seen as threats or opportunities. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_roadmap" name="roadmap">roadmap</a></b>
</dt>
<dd>A specialized type&nbsp;of&nbsp;<a  class="elementLinkWithUserText" href="#guidance" guid="_83ttAB_NEdq6CKKKq4D7YA" >guidance</a>&nbsp;that is specific to a process that represents a linear walkthrough of those items from a particular perspective.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_role" name="role">role</a></b>
</dt>
<dd><p>     Describes a standard set of responsibilities and corresponding skills necessary to perform a task&nbsp;or create a work     product.&nbsp; A Role is <strong>not</strong> a job description the same person may execute several roles     simultaneously or during the course of a project and a role may likewise be defined to represent a group such as a     review board. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_role_set" name="role_set">role set</a></b>
</dt>
<dd>A specialized type of category used to organize <a  class="elementLinkWithUserText" href="#role" guid="_yUefQNnmEdmO6L4XMImrsA" >roles</a> by certain commonalities such as type of work, profession or area of knowledge.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_role_set_grouping" name="role_set_grouping">role set grouping</a></b>
</dt>
<dd>A specialized category used to organize role sets.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_S" name="S">S</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_scope" name="scope">scope</a></b>
</dt>
<dd><p>     The boundaries for inclusions and exclusions that define the depth and breadth of the project. Example of areas for     consideration are included functionality, affected organizations, lifecycle phases performed, included and excluded     deliverables, involved geographic areas, and so on. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_stakeholder_need" name="stakeholder_need">stakeholder need</a></b>
</dt>
<dd>The business or operational problem (opportunity) that must be fulfilled to justify purchase or use of the system.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_step" name="step">step</a></b>
</dt>
<dd>Sub-section of a <a  class="elementLink" href="#task" guid="_x459ktnmEdmO6L4XMImrsA" >task</a>&nbsp;used to organize the work to be performed to achieve the overall goal of the task. Not all Steps are necessarily performed each time a task is executed in a process.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_supporting_material" name="supporting_material">supporting material</a></b>
</dt>
<dd>A&nbsp;<a  class="elementLinkWithUserText" href="#guidance" guid="_83ttAB_NEdq6CKKKq4D7YA" >guidance</a>&nbsp;that is a catch-all for other types of guidance not specifically defined elsewhere.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_system_wide_requirement" name="system_wide_requirement">system-wide requirements</a></b>
</dt>
<dd>System-wide requirements are requirements that&nbsp;define necessary system quality attributes&nbsp;such as performance, usability and reliability, as well as global functional requirements&nbsp;that are not captured in behavioral requirements artifacts such as use-cases.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_T" name="T">T</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_task" name="task">task</a></b>
</dt>
<dd><p>     Defines a unit of work that needs to be done in order to&nbsp;transfrom inputs into outputs through a series&nbsp;of     steps&nbsp;performed by one or more roles&nbsp;independent of a particular work breakdown structure (WBS). </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_team_profile" name="team_profile">team profile</a></b>
</dt>
<dd>A&nbsp;<a  class="elementLinkWithUserText" href="#breakdown_element" guid="_cvdpEB_LEdq6CKKKq4D7YA" >breakdown element</a> that groups role descriptors or composite roles, thus defining a nested hierarchy of teams and team members.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_template" name="template">template</a></b>
</dt>
<dd>A specialized type of <a  class="elementLinkWithUserText" href="#guidance" guid="_83ttAB_NEdq6CKKKq4D7YA" >guidance</a>&nbsp;that specifies the structure of a work product by providing a pre-defined table of contents, sections, packages, and/or headings, a standardized format, as well as descriptions on how the sections and packages are supposed to be used and completed.&nbsp; Often provided as a form or empty instanced of a work product that can be used as starting point for the creation of a new one.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_term_definition" name="term_definition">term definition</a></b>
</dt>
<dd>A specialized form of&nbsp;<a  class="elementLinkWithUserText" href="#guidance" guid="_83ttAB_NEdq6CKKKq4D7YA" >guidance</a>&nbsp;that provides definitions that are used to build up the glossary</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_tool" name="tool">tool</a></b>
</dt>
<dd>A&nbsp;standard category used as a container for <a  class="elementLinkWithUserText" href="#tool_mentor" guid="_yYy-mdnmEdmO6L4XMImrsA" >tool mentors</a>. It can also provide general descriptions of the tool and its general capabilities.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_tool_mentor" name="tool_mentor">tool mentor</a></b>
</dt>
<dd>A tool mentor is a type of <a  class="elementLink" href="#guidance" guid="_83ttAB_NEdq6CKKKq4D7YA" >guidance</a>&nbsp;that explains how to appy a specific tool to accomplish a <a  class="elementLink" href="#task" guid="_x459ktnmEdmO6L4XMImrsA" >task</a>, perform&nbsp;a set of&nbsp;<a  class="elementLink" href="#step" guid="_BqZloB_eEdqAHrsQ7-jSbw" >step</a>s or instantiate a particular <a  class="elementLink" href="#work_product" guid="_H4JXwB_SEdq6CKKKq4D7YA" >work product</a>.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_transition" name="transition">Transition</a></b>
</dt>
<dd>The fourth and last <span class="docEmphasis">phase</span> of the project lifecycle, which results in a final product <span class="docEmphasis">release</span>.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_U" name="U">U</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_uma" name="uma">UMA</a></b>
</dt>
<dd>Stands for&nbsp;Unified Method&nbsp;Architecture. UMA is a state-of-the-art architecture for the conceiving, specifying, and storing of method and process metadata.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_use_case_scenario" name="use_case_scenario">use-case scenario</a></b>
</dt>
<dd>Represents specific instances of the use case that correspond to specific inputs from the Actor or to specific conditions in the environment. Each scenario describes alternate ways that the system provides a behavior, or it may describe failure or exception cases</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_V" name="V">V</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_velocity" name="velocity">Velocity</a></b>
</dt>
<dd>A key metric used for iteration planning. It indicates how many points are delivered upon within an iteration for a certain team and project.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_version" name="version">version</a></b>
</dt>
<dd>A variant of some artifact; later versions of an artifact typically expand upon earlier versions.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_view" name="view">view</a></b>
</dt>
<dd>Structured content collections designed to drive publication and facilitate browsing. They are specified using <a  class="elementLinkWithUserText" href="#custom_category" guid="_eqw94MaFEduMlb2cQZNTYw" >custom categories</a>.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_W" name="W">W</a></b>
</dt>
<dd></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_white_paper" name="white_paper">white paper</a></b>
</dt>
<dd><p>     A specialized type of&nbsp;<a  class="elementLinkWithUserText" href="#guidance" guid="_83ttAB_NEdq6CKKKq4D7YA" >guidance</a>&nbsp;for externally&nbsp;published papers&nbsp;that can be read and     understood in isolation of other content elements. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_work_breakdown_structure" name="work_breakdown_structure">work breakdown structure (WBS)</a></b>
</dt>
<dd><p>     A hierarchical structured list of all the project activities, in which the work of the project is broken down into     smaller work units to achieve an appropriate level of granularity that ensures that the full scope of work to be     performed is understood. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_work_item" name="work_item">Work Item</a></b>
</dt>
<dd>Scheduled work to be done within the project.</dd>
<dt>
<b><a id="_GLOSSARY_ITEM_work_product" name="work_product">work product</a></b>
</dt>
<dd><p>     Used to define and describe the items needed as input or created as output of one or more&nbsp;<a  class="elementLink" href="#task" guid="_x459ktnmEdmO6L4XMImrsA" >task</a>s that are the responsibility of a single role.&nbsp; See: <a  class="elementLink" href="#artifact" guid="_x7cUM9nmEdmO6L4XMImrsA" >artifact</a>, <a  class="elementLink" href="#deliverable" guid="_yFbWoNnmEdmO6L4XMImrsA" >deliverable</a>, <a  class="elementLink" href="#outcome" guid="_LNAAcB_iEdqAHrsQ7-jSbw" >outcome</a>. </p></dd>
<dt>
<b><a id="_GLOSSARY_ITEM_work_product_kind" name="work_product_kind">work product kind</a></b>
</dt>
<dd>A specialized type of category used to organized <a  class="elementLink" href="#work_product" guid="_H4JXwB_SEdq6CKKKq4D7YA" >work product</a>s based on their intended usage&nbsp;or type.</dd>
</dl>
</font>
</body>
</html>
